Sync Ubuntu 26.04 support to release/1.3.x - #138
Merged
sgopinath1 merged 3 commits intoJul 29, 2026
Conversation
Map the UBUNTU_VERSION codename "resolute" to version number 26.04 so `make pkg-deb UBUNTU_VERSION=resolute` produces a 26.04-tagged package, alongside the existing jammy (22.04) and noble (24.04) targets. The Ubuntu 26.04 base image ships a default non-root user occupying UID 1000, which collides with the host UID the build entrypoint tries to recreate. Detect and remove any pre-existing user holding the requested UID before creating the build user. This is a no-op on 22.04/24.04 images, which have no such default user. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
Ubuntu 26.04 (Resolute) packages are already published for 1.3.0 on repo.radeon.com and install cleanly, but the docs still listed only 22.04 and 24.04. Add 26.04 to the supported OS list, the 1.3.0 compatibility matrix row, and the README requirements. Older matrix rows are left unchanged since those releases were never built for 26.04. No version bump is needed. 26.04 support came from the build matrix addition in ROCm#134, not a code change.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Backports Ubuntu 26.04 (Resolute) support from
mainto the 1.3 release line.release/1.3.xcurrently has neither the build support nor the docs, so it cannot produce a 26.04 package even though1.3.0~26.04is already published onrepo.radeon.com.Three commits cherry-picked cleanly, no conflicts, original authorship preserved:
Add Ubuntu 26.04 (resolute) Debian package build supportUBUNTU_VERSION=resoluteto26.04; remove a pre-existing user occupying the requested UID in the build entrypointGuard UID lookup so build entrypoint works without a default UID 1000 userDocument Ubuntu 26.04 support for 1.3.05 files, +13/-2.
Verification
Makefileandtools/deb/base-image/entrypoint.share byte-identical tomainafter the cherry-picks.--device amd.com/gpuand Docker 29 native--gpus, OCI runtime injection via--runtime=amdwithAMD_VISIBLE_DEVICESrunningrocminfo/amd-smi, and GPU Tracker enable/alloc/exclusive-enforcement/auto-release/reset.Test plan
make pkg-deb UBUNTU_VERSION=resoluteproduces a26.04-tagged package on this branch.make pkg-deb UBUNTU_VERSION=jammyandUBUNTU_VERSION=noblestill build, confirming the entrypoint guard is a no-op there.Note
Merge #137 into
mainfirst if you wantmainandrelease/1.3.xto stay consistent, since this PR carries that docs commit.